fix(analyze): respect --log-level in output and JSON#194
Merged
Conversation
commit: |
dreyfus92
changed the title
--log-level in output and JSON
43081j
reviewed
Mar 23, 2026
43081j
reviewed
Apr 23, 2026
| description: | ||
| 'Only show errors in Results and JSON messages (same idea as ESLint --quiet). Overrides --report-level.' | ||
| }, | ||
| 'report-level': { |
Contributor
There was a problem hiding this comment.
maybe this should just be severity?
There was a problem hiding this comment.
I think report-level makes sense in this case
43081j
approved these changes
Apr 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
this wires
--log-levelthrough to what you actually see: pretty analyze output and the messages array in--jsonnow only include severities at or above the chosen level, so stuff like--log-levelerror finally hides warnings/suggestions instead of feeling broken. If you still want the full diagnostic list in JSON but need a stricter exit code, there’s--json-fullfor that. Unknown message severities are treated like warnings so nothing silently disappears.closes: #192